Apparatuses and methods for concurrently accessing different memory planes of a memory

ABSTRACT

Apparatuses and methods for concurrently accessing different memory planes are disclosed herein. An example apparatus may include a controller associated with a queue configured to maintain respective information associated with each of a plurality of memory command and address pairs. The controller is configured to select a group of memory command and address pairs from the plurality of memory command and address pairs based on the information maintained by the queue. The example apparatus further includes a memory configured to receive the group of memory command and address pairs. The memory is configured to concurrently perform memory access operations associated with the group of memory command and address pairs.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 14/340,976, filed Jul. 25, 2014. This application is incorporated by reference herein in its entirety and for all purposes.

BACKGROUND

Memories may be provided in a variety of apparatuses, such as computers or other devices, including but not limited to portable memory devices, solid state drives, music players, cameras, phones, wireless devices, displays, chip sets, set top boxes, gaming systems, vehicles, and appliances. There are many different types of memory including volatile memory (e.g., dynamic random access memory (DRAM)) and non-volatile memory (e.g., flash memory). Flash memory architectures may include NAND or NOR architecture.

In non-volatile memories (e.g., NAND flash memories), memory arrays may be divided into planes. Dividing a memory into planes may break up rows or columns into smaller sections for accessing during memory access operations. Breaking the memory up into planes may also present an opportunity to access more than one portion of the memory array concurrently. Typically, concurrent access may require access of memory cells that are coupled to the same respective access line driver, which may limit an ability to concurrently access different planes during random memory access requests.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a memory system according to an embodiment of the present disclosure.

FIG. 2 is a block diagram of a memory system according to an embodiment of the present disclosure.

FIG. 3 is an exemplary table of a queue according to an embodiment of the present disclosure.

FIG. 4 is a block diagram of an apparatus including a memory according to an embodiment of the present disclosure.

FIG. 5 is a block diagram of an apparatus including a memory according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Apparatuses and methods for concurrent access of different memory planes are disclosed herein. Certain details are set forth below to provide a sufficient understanding of embodiments of the disclosure. However, it will be clear to one having skill in the art that embodiments of the disclosure may be practiced without these particular details. Moreover, the particular embodiments of the present disclosure described herein are provided by way of example and should not be used to limit the scope of the disclosure to these particular embodiments. In other instances, well-known circuits, control signals, timing protocols, and software operations have not been shown in detail in order to avoid unnecessarily obscuring the disclosure.

FIG. 1 is a block diagram of an apparatus 100 (e.g., an integrated circuit, a memory device, a memory system, an electronic device or system, a smart phone, a tablet, a computer, a server, etc.) according to an embodiment of the present disclosure. The apparatus 100 may include a controller 110 (e.g., memory controller) and a memory 150. The controller 110 and the memory 150 may be coupled by a command, address, and data (CAD) bus 130. The memory 150 may be configured to receive commands and/or addresses from the controller 110 over the CAD bus 130, and the memory may be configured to receive data and/or provide data over the CAD bus 130.

In some examples, the memory 150 may be a non-volatile memory, such as NAND, NOR, or PCM flash memory. The memory 150 may include an array of cells organized in multiple memory planes (e.g., partitions). The memory planes may be divided into blocks of memory cell pages. Each page may include a row or column of memory cells that are coupled to a respective access line. The memory 150 may provide voltage on an access line during a memory access operation to erase, program, and/or read from a page of memory cells. The access line voltages required to access data of a page of memory cells may depend on a page type. A page type may be based on a type of memory cell in the page (e.g., SLC, MLC, TLC, etc.) and a level of the memory cells being accessed (e.g., upper page UP, lower page LP, middle page MP, single level cell page). The memory 150 may include circuitry that performs concurrent memory page accesses for two or more memory planes when the memory pages have a common page type. In some embodiments, the memory page accesses are concurrent, for example, when memory access operations for the respective memory pages at least partially temporally overlap. While the memory access operations for the respective memory pages may occur simultaneously, embodiments of the disclosure are not limited to simultaneous memory access operations.

The controller 110 may be associated with (e.g., include) a queue that stores information associated with a plurality of memory command and address pairs. The controller 110 may select a group of command and address pairs from the plurality of memory command and address pairs based on the information stored in the queue. The information stored in the queue for each of the plurality of command and address pairs may include an associated memory plane, and/or an associated page type. The controller 110 may select a group of memory commands and addresses based on the associated memory plane and/or page type.

The memory 150 may be configured to perform concurrent memory operations (e.g., read operations or program operations) for memory planes associated with the received memory command and address pairs. For example, when the group of memory command and address pairs are read commands associated with a common page type, the memory 150 may provide read data associated with each memory command and address pair to the controller 110 over the CAD bus 130. Further, when the group of memory command and address pairs are program commands associated with a common page type, the memory 150 may receive and program data associated with each memory command and address pair. Additionally, the memory 150 may further provide information to the controller 110 over the CAD bus 130 in response to particular commands. The information may indicate, for instance, whether the memory 150 is available to perform a memory operation and/or an amount of time before the memory 150 may become available to perform a memory operation.

During operation, the queue associated with the controller 110 may maintain (e.g., store) information associated with each of a plurality of memory command address pairs. The controller 110 may select a group of memory command and address pairs from the plurality of memory command and address pairs based on the information maintained by the queue. As previously described, in some examples, the information may include memory plane and/or page type, and the controller 110 may select a group of memory command and address pairs based on the plane and/or page type associated with each memory command and address pair. For example, the controller 110 may select a command and address pair to add to the group when associated with a memory plane that is different than the memory planes associated with other command and address pairs of the group, and/or when the command and address pair associated with a page type that is common with the other command and address pairs of the group. The controller 110 may continue to select command and address pairs to be added to the group until an end of the queue is reached or until the group includes a command and address pair directed to each memory plane of the memory 150. In the latter case, the selected group including a command and address pair directed to each memory plane of the memory 150 may facilitate a fully concurrent memory access at the memory 150 (e.g., concurrent memory access of each memory plane of the memory 150). The controller 110 may provide the selected group of memory command and address pairs to the memory 150 via the CAD bus 130 in parallel or serially.

The memory 150 may be configured to concurrently perform memory access operations for memory command and address pairs associated with common page types across two or more memory planes. Typically, during a memory access operation, a procedure for accessing data of a page may be dependent on a page type. That is, to read data from an MLC or TLC page, read voltages that may be provided (e.g., applied) may depend on which level (e.g., bit) of each memory cell of the page is being read. For example, if a bit in the UP of an MLC page is being read, a first read voltage may be provided to the associated access line during the read operation. If a bit in the LP of an MLC page is being read, a second and/or a third read voltage may be provided to the associated access line during the read operation.

Thus, by grouping the memory command and address pairs according to memory plane and page type, the memory 110 may be able to use the same process to retrieve data from the each page associated with the group of memory command and address pairs. That is, the same voltages may be provided to each of the addressed pages. By using the same process to retrieve data from each memory plane, the concurrent access may be performed without necessarily including individual internal controllers for each memory plane or a single multi-thread controller in the memory 150.

FIG. 2 is a block diagram of an apparatus 200 according to an embodiment of the present disclosure. The apparatus 200 may include a controller 210 (e.g., memory controller) and a memory 250. The controller 210 may implemented in the controller 110 of FIG. 1, and the memory 250 may be implemented in the memory 150 of FIG. 1. The controller 210 and the memory 250 may be coupled by a command, address, and data (CAD) bus 230. The memory 250 may be configured to receive commands and/or addresses from the controller 210 over the CAD bus 230, and the memory may be configured to receive data and/or provide data over the CAD bus 230. It is understood that the CAD bus 230 may include one or more separate busses for the command, addresses, and data.

In some examples, the memory 250 may be a non-volatile memory, such as NAND, NOR, or PCM flash memory. The memory 250 may include an internal controller 260 coupled to a memory array 270. The memory array 270 may be organized into memory planes, with each memory plane having respective memory cell blocks. Each memory cell block may have a number of pages (e.g., rows or columns) of memory cells corresponding to a number of access lines. In some embodiments, the memory array 270 may include memory cells that are SLCs, MLCs, TLCs, or combinations thereof.

The internal controller 260 may control memory circuitry for concurrently accessing an individual page of different memory planes of the memory array 270 responsive to a group of memory access command and address pairs received from the 210. For example, the memory 250 may include individual access line driver circuits for each memory plane of the memory array 270. Each individual access line driver circuit may be coupled to the respective memory plane via a respective plurality of global access lines. When more than one memory command and address pair is received at the memory 250 that are each associated with different memory planes of the memory array 270, the internal controller 260 may concurrently provide signals to the individual access line driver circuits of the addressed memory planes to control voltages provided to the corresponding respective plurality of global access lines during memory access operations to erase, program, and/or read from the addressed pages of the different memory planes.

The controller 210 may be associated with a queue 220 that stores information associated with each of a plurality of memory command and access pairs. The controller 210 may select a group of memory command and address pairs from the plurality of memory command and address pairs based on the information stored in the queue 220. The information stored in the queue 220 for each of the plurality of memory command and address pairs may include several fields. For example, the queue 220 may store associated memory plane and page type information for each memory command and address pair. The controller 210 may select the group of commands and address pairs from the plurality of memory command and address pairs from the queue 220 to provide to the memory 250 based on the memory planes and/or page type associated with the command and address pairs of the group.

During operation, the controller 210 may maintain the queue 220 that includes information associated with a plurality of memory command and address pairs. FIG. 3 depicts an exemplary implementation of the queue 220. For example, the example queue 220 depicted in FIG. 3 may include three fields: an address field 310, a memory plane field 320, and a page type field 330. In some embodiments, the example queue 220 may be configured to store information for up to eight memory command and address pairs. It will be appreciated that the queue 220 may have more or less than three fields, and may be configured to store information associated with more or less than eight command and address pairs.

The controller 210 may select a group of memory command and address pairs from the plurality of memory command and address pairs based on the information stored in the queue 220. For example, the controller 210 may select the group of memory command and address pairs from the plurality of memory command and address pairs based on the associated memory plane and/or the associated page type associated with each memory command and address pair. In some examples, the controller 210 may select a command and address pair to add to the group when it is directed to a different memory plane than the other command and address pairs of the group, and is associated with a common page type as the other command and address pairs of the group. The controller 210 may continue to select memory command and address pairs to add to the group until an end of the queue 220 is reached or until the group includes a command and address pair directed to each memory plane of the memory cell 250.

In some embodiments, the controller 210 may generally select memory command and address pairs that meet the earlier described criteria of different memory planes and same page type using a first in, first out (FIFO) methodology. For example, a first selected memory command and address pair of the selected group may be an oldest memory command and address pair included in the queue 220, with additional selections added on a FIFO basis.

In the example provided in FIG. 3, a first entry ADDR0, directed to PLANE0 and having a LP page type, may be selected for a group. The second entry ADDR1, directed to PLANE0 and having a LP page type, may be skipped for the group because the plane is the same as the PLANE0 of ADDR0. The third entry ADDR2, directed to PLANE1 and a LP page type, may be selected for the group because the memory plane is different than the PLANE0 of ADDR0 and the LP page type matches the LP page type of ADDR0. The fourth entry ADDR3, directed to PLANE2 and having an UP page type, may be skipped for the group because the UP page type is different than the LP page type of ADDR0. The fifth entry ADDR4, directed to PLANE2 and having the LP page type, may be selected for the group because the memory plane is different than the PLANE0 of ADDR0 and the PLANE1 of ADDR2 and the LP page type matches the LP page type of ADDR0. The sixth entry ADDR5, directed to PLANE0 and having a LP page type, may be skipped for the group because the memory plane is the same as the PLANE0 of ADDR0. The seventh entry ADDR5, directed to PLANE3 and having the LP page type, may be selected for the group because the memory plane is different than the PLANE0 of ADDR0, the PLANE1 of ADDR2, and the PLANE2 of ADDR4, and the LP page type matches the LP page type of ADDR0. The eighth entry ADDR7, directed to PLANE2 and having a LP page type, may be skipped for the group because the memory plane is the same as the PLANE2 of ADDR4. Thus, the selected group of memory command and address pairs may include ADDR0, ADDR2, ADDR4, and ADDR6 based on the examples provided in FIG. 3.

The controller 210 may provide the selected group of memory command and address pairs to the memory 250 via the 230 CAD bus. The internal controller 260 may be configured to perform concurrent memory operations (e.g., read operations or program operations) for different memory planes of the memory array 270 in response to the received group of memory command and address pairs.

As previously described, the memory 250 may include individual access line circuits coupled to each memory plane via respective global access lines. The memory 250 may be configured to concurrently perform memory access operations for addresses associated with common page types in different memory planes of the memory array 270. Thus, when the group of memory command and address pairs are associated with a common page type, the process for accessing each address pages is the same, and the internal controller 260 provides (e.g., sends) signals to each individual access line driver circuit to provide voltages to respective global access lines associated with the addressed pages. The individual access line driver circuits may allow different respective pages within different respective blocks of memory cells to be accessed concurrently. For example, a first page of a first block of a first memory plane may be accessed concurrently with a second page of a second block of a second memory plane, provided the second page has a common page type as the first page.

FIG. 4 illustrates a memory 400 according to an embodiment of the present disclosure. The memory 400 includes a memory array 430 with a plurality of memory cells. The memory cells may be non-volatile memory cells, such as NAND flash cells, or may generally be any type of memory cells. The memory 400 may include the memory 150 of FIG. 1 and/or the memory 250 of FIG. 2. In some examples, the memory array 430 may be divided into a plurality of memory planes.

Command signals, address signals and data signals may be provided to the memory 400 as sets of sequential input/output (“I/O”) signals transmitted through an I/O bus 428. Similarly, data signals may be provided from the memory 400 through the I/O bus 428. The I/O bus 428 is connected to an I/O control unit 420 that provides (e.g., routes) the signals between the I/O bus 428 and an internal data bus 422, an internal address bus 424, and an internal command bus 426. The memory 400 also includes a control logic unit 410 that receives a number of control signals either externally or through the command bus 426 to control the operation of the memory 400. The combination of the control logic unit 410 and the I/O control unit 420 may facilitate concurrent memory access of different memory planes of the memory array 430.

The address bus 424 provides block-row address signals to a row decoder 440 and column address signals to a column decoder 450. The row decoder 440 and column decoder 450 may be used to select blocks of memory or memory cells for memory operations, for example, read, program, and erase operations. The column decoder 450 may enable data signals to be provided to columns of memory corresponding to the column address signals and allow data signals to be provided from columns corresponding to the column address signals. In some examples, the column decoder 450 and/or the row decoder 440 may include individual access line driver circuits for each memory plane of the memory array 430. The individual access line driver circuits may be coupled to the respective memory planes via a respective plurality of global access lines.

In response to the memory commands decoded by the control logic unit 410, the memory cells in the array 430 are read, programmed, or erased. Read, program, erase circuits 468 coupled to the memory array 430 receive control signals from the control logic unit 410 and include voltage generators for providing various voltages for read, program, and erase operations.

After the row address signals have been provided to the address bus 424, the I/O control unit 420 provides (e.g., routes) data signals to a cache register 470 for a program operation. The data signals are stored in the cache register 470 in successive sets each having a size corresponding to the width of the L/O bus 428. The cache register 470 sequentially stores the sets of data signals for an entire page (e.g., row) of memory cells in the array 430. All of the stored data signals are then used to program a page of memory cells in the array 430 selected by the block-row address coupled through the address bus 424. In a similar manner, during a read operation, data signals from a page of memory cells selected by the block-row address coupled through the address bus 424 are stored in a data register 480. Sets of data signals corresponding in size to the width of the I/O bus 428 are then sequentially transferred through the I/O control unit 420 from the cache register 470 to the I/O bus 428.

FIG. 5 illustrates a portion of memory 500 according to an embodiment of the present disclosure. The memory 500 includes a memory array 570 with a plurality of memory planes 572(0)-572(3) that each includes a respective plurality of memory cells. The memory 500 may be implemented in the memory 150 of FIG. 1, the memory 250 of FIG. 2, and/or the memory 400 of FIG. 4. The memory cells may be non-volatile memory cells, such as NAND flash cells, or may generally be any type of memory cells.

The memory planes 572(0)-572(3) may each be divided into blocks of data, with a different relative block of data from each of the memory planes 572(0)-572(3) concurrently accessible during memory access operations associated with a common page type. For example, during memory access operations associated with a common page type, data block 582 of the memory plane 572(0), data block 583 of the memory plane 572(1), data block 584 of the memory plane 572(2), and data block 585 of the memory plane 572(3) may each be accessed concurrently.

Each of the memory planes 572(0)-572(3) may be coupled to a respective page buffer PB0-PB3 576(0)-(3), respectively. Each PB0-PB3 576(0)-576(3) may be configured to provide data to or receive data from the respective memory plane 572(0)-572(3). The PB0-PB3 576(0)-576(3) may be controlled by the internal controller 560.

Each of the memory planes 572(0)-572(3) may be further coupled to a respective access line driver circuit 574(0)-574(3), respectively. The A/L driver circuits 574(0)-574(3) may be configured to condition a page of a respective block of an associated memory plane 572(0)-572(3) for a memory access operation, such as programming data, reading data, or erasing data. The A/L driver circuits 574(0)-574(3) may be controlled based on signals from the internal controller 560. Each of the A/L driver circuits 574(0)-(3) may be coupled to a power circuit 580, and may provide voltages to respective wordlines based on voltages provided by the power circuit 580. The voltages provided by the power circuit 580 may be based on signals received from the internal controller 560.

The internal controller 560 may control the A/L driver circuits 574(0)-574(3), page buffers PB0-PB3 576(0)-576(3), and the power circuit 580 to concurrently perform memory access operations associated with each of a group of memory command and address pairs (received from a controller, such as the controller 110 of FIG. 1 and/or the controller 210 of FIG. 2). For example, the internal controller 560 may control the A/L driver circuits 574(0)-574(3), the page buffers PB0-PB3 576(0)-576(3), and the power circuit 580 to perform the concurrent memory access operations. The internal controller 560 may be implemented in the control logic unit 410 and/or the I/O control unit 420 of FIG. 4, for example.

In operation, the internal controller 560 may receive a group of memory command and address pairs, with each pair arriving in parallel or serially. In some examples, the group of memory command and address pairs are each associated with a common page type and different respective memory planes 572(0)-572(3) of the memory array 570. The internal controller 560 may be configured to perform concurrent memory operations (e.g., read operations or program operations) across the different memory planes 572(0)-572(3) of the memory array 570 responsive to the group of memory command and address pairs.

For example, the internal controller 560 may provide signals to the A/L driver circuits 574(0)-574(3) that are coupled to the memory planes 572(0)-572(3) associated with the group of memory command and address pairs. The internal controller 560 may also provide (e.g., send) signals to the power circuit 580, and the power circuit 580 may provide voltages to the A/L driver circuits 574(0)-574(3). The voltages provided by the power circuit 580 may depend on a page type associated with the memory access operations. The power circuit 580 may be configured to concurrently perform memory access operations for addresses associated with common page types in each memory plane 572(0)-572(3) of the memory array 570. Thus, when the group of memory command and address pairs are associated with a common page type, the process for accessing each address pages is common, and the internal controller 560 provides signals to associated individual A/L driver circuits 574(0)-574(3) to provide voltages to global access lines associated with the addressed pages.

As previously described, each A/L driver circuit 574(0)-574(3) may be coupled to a respective memory plane 572(0)-572(3) via respective global access lines. Thus, based on the signals received from the internal controller 560, the A/L driver circuits 574(0)-574(3) that are coupled to the memory planes 572(0)-572(3) associated with the group of memory command and address pairs may select blocks of memory or memory cells from each associated memory plane 572(0)-572(3), for memory operations, such as read, program, and/or erase operations. The individual A/L driver circuits 574(0)-574(3) may drive different respective global access lines within the respective plurality of global access lines. As an example, the A/L driver circuit 574(0) may drive a first voltage on a first global access line of a first plurality of global access lines, the A/L driver circuit 574(1) may drive the first voltage on a third global access line of a second plurality of global access lines, the A/L driver circuit 574(2) may drive the first voltage on a seventh global access line of a third plurality of global access lines, etc., and second voltages may be driven on each of the remaining global access lines of the first, second, third, etc., plurality of global access lines. The individual A/L driver circuits may allow different respective pages within different respective blocks of memory cells to be accessed concurrently. For example, a first page of a first block of a first memory plane may be accessed concurrently with a second page of a second block of a second memory plane, provided the second page has a common page type as the first page.

The page buffers PB0-PB3 576(0)-576(3) may provide data to or receive data from the internal controller 560 during the memory access operations responsive to signals from the internal controller 560 and the respective memory planes 572(0)-572(3). The internal controller 560 may provide the received data to a controller, such as the controller 110 of FIG. 1 and/or the controller 210 of FIG. 2.

It will be appreciated that the memory 500 may include more or less than four memory planes, A/L drivers, and page buffers. It will also be appreciated that the respective plurality of global access lines may include 8, 16, 32, 64, 128, etc., global access lines. The internal controller 560 and the individual A/L driver circuits 574(0)-574(3) may allow accessing different respective pages within different respective blocks of different memory planes concurrently when the different respective pages are of a common page type, which may improve concurrent access during random addressing of the memory 500.

From the foregoing it will be appreciated that, although specific embodiments of the disclosure have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the disclosure. Accordingly, the disclosure is not limited except as by the appended claims. 

What is claimed is:
 1. An apparatus, comprising: a controller coupled to a memory via a command, address, and data bus, the controller including a queue configured to maintain respective information associated with each of a plurality of memory command and address pairs, wherein the respective information associated with each of the plurality of memory command and address pairs includes a corresponding memory plane identifier of a memory plane of the memory and a corresponding page type identifier that indicates a level of memory cells of the memory being accessed, wherein, using the respective information maintained in the queue, the controller is configured to provide a selected group of memory command and address pairs of the plurality of memory command address pairs to an internal controller of the memory, wherein the controller is configured to use the respective information maintained in the queue to identify individual memory command and address pairs of the plurality of memory command address pairs capable of being concurrently executed by the memory for inclusion in the selected group of memory command and address pairs.
 2. The apparatus of claim 1, wherein the controller is configured to select the group of memory command and address pairs from the memory command and address pairs based on a first in, first out, methodology.
 3. The apparatus of claim 1, wherein the queue is configured to store the corresponding memory plane identifier in a first field for an entry corresponding to one of the plurality of memory command and address pairs.
 4. The apparatus of claim 3, wherein the queue is configured to store the corresponding page type identifier in a second field for the entry corresponding to the one of the plurality of memory command and address pairs.
 5. The apparatus of claim 4, wherein the queue is configured to store an address identifier in a third field for the entry corresponding to the one of the plurality of memory command and address pairs.
 6. The apparatus of claim 1, wherein the selected group of memory command and address pairs are each associated with a different memory plane identifier.
 7. The apparatus of claim 1, wherein the selected group of memory command and address pairs are each directed to a common page type identifier.
 8. The apparatus of claim 1, wherein the corresponding page type identifier indicates an upper page or a lower page.
 9. The apparatus of claim 1, wherein the memory includes non-volatile memory.
 10. The apparatus of claim 1, wherein commands of each of the selected group of memory command and address pairs are one of a program command, a read command, or an erase command.
 11. A method, comprising: maintaining, at a controller coupled to a memory via a bus, a queue that includes respective information associated with each of a plurality of memory command and address pairs to be executed at the memory, wherein the respective information associated with each of a plurality of memory command and address pairs includes a corresponding memory plane identifier of a memory plane of the memory and a corresponding page type identifier that indicates a level of memory cells of the memory being accessed; and electing individual memory command and address pairs of the plurality of memory command address pairs capable of being concurrently executed at the memory for inclusion in a selected group of memory command and address pairs; and providing the selected group of memory command and address pairs to the memory.
 12. The method of claim 11, further comprising selecting the individual memory command and address pairs of the plurality of memory command address pairs having a common page type identifier for inclusion in the selected group of memory command and address pairs.
 13. The method of claim 12, further comprising selecting the individual memory command and address pairs of the plurality of memory command address pairs associated a different respective memory plane identifier for inclusion in the selected group of memory command and address pairs.
 14. The method of claim 11, further comprising storing, in the queue, the corresponding memory plane identifier in a first field for an entry corresponding to one of the plurality of memory command and address pairs.
 15. The method of claim 14, further comprising storing, in the queue, the corresponding page type identifier in a second field for the entry corresponding to the one of the plurality of memory command and address pairs.
 16. The method of claim 15, further comprising storing, in the queue, an address identifier in a third field for the entry corresponding to the one of the plurality of memory command and address pairs.
 17. The method of claim 11, further comprising selecting the individual memory command and address pairs of the plurality of memory command address pairs for inclusion in the selected group of memory command and address pairs based on a first in, first out, methodology.
 18. The method of claim 11, wherein the corresponding page type identifier indicates an upper page or a lower page.
 19. The method of claim 11, wherein the memory includes non-volatile memory.
 20. The method of claim 1, wherein commands of each of the selected group of memory command and address pairs are one of a program command, a read command, or an erase command. 